Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 85be1045a298bd3703cc34263f36b017b6b441e1722d03abdc5bcbc40e82c7f4

Tx prefix hash: 32343724d3767ace55d058398718a55398dbf3186820d9b0689743464cd0379a
Tx public key: e876dec6424d6e75f8e5f8199c2e9c10d7e22a0c077e9edb4b4adeec1d42241e
Timestamp: 1582508560 Timestamp [UCT]: 2020-02-24 01:42:40 Age [y:d:h:m:s]: 04:306:07:15:07
Block: 71106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111663 RingCT/type: yes/0
Extra: 01e876dec6424d6e75f8e5f8199c2e9c10d7e22a0c077e9edb4b4adeec1d42241e021100000001c71d3ff9000000000000000000

1 output(s) for total of 356.777211286000 dcy

stealth address amount amount idx
00: a17af48b529dca54ba9a88c64984b55ce7fe76365aeeb13f84d3d5a78082f046 356.777211286000 131421 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 71116, "vin": [ { "gen": { "height": 71106 } } ], "vout": [ { "amount": 356777211286, "target": { "key": "a17af48b529dca54ba9a88c64984b55ce7fe76365aeeb13f84d3d5a78082f046" } } ], "extra": [ 1, 232, 118, 222, 198, 66, 77, 110, 117, 248, 229, 248, 25, 156, 46, 156, 16, 215, 226, 42, 12, 7, 126, 158, 219, 75, 74, 222, 236, 29, 66, 36, 30, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8