Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc73871cc37ccd1b87c87d84b4e45cd93c6810fcbaa1e9f9ad8531b4354139a8

Tx prefix hash: e92f0b8d906403998a0ec02afdd4815ea86026e76fe4a31af5ed9945ebe48c35
Tx public key: ca8c18f0672a2d51aff1aadabefb8330c84254de7e69e9dba81e5406742fb84f
Timestamp: 1578318709 Timestamp [UCT]: 2020-01-06 13:51:49 Age [y:d:h:m:s]: 05:104:15:49:05
Block: 39707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224934 RingCT/type: yes/0
Extra: 01ca8c18f0672a2d51aff1aadabefb8330c84254de7e69e9dba81e5406742fb84f021100000220391a8d0e000000000000000000

1 output(s) for total of 453.359327630000 dcy

stealth address amount amount idx
00: 8170c77243ef2d7097eedf48a15707001215b8f2b5c552bf692eac342e8f9b62 453.359327630000 68887 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": 39717, "vin": [ { "gen": { "height": 39707 } } ], "vout": [ { "amount": 453359327630, "target": { "key": "8170c77243ef2d7097eedf48a15707001215b8f2b5c552bf692eac342e8f9b62" } } ], "extra": [ 1, 202, 140, 24, 240, 103, 42, 45, 81, 175, 241, 170, 218, 190, 251, 131, 48, 200, 66, 84, 222, 126, 105, 233, 219, 168, 30, 84, 6, 116, 47, 184, 79, 2, 17, 0, 0, 2, 32, 57, 26, 141, 14, 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