Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 678f53c0d293f4d2f0bb331d81c571227ba0f396909dad19c1eb5dafcf473eb0

Tx prefix hash: c4c96fc4611d38a3598c698ed8057cd2a6f9e929eb0ae1db808ad9d8d5f1c66b
Tx public key: 3d208871bb8205c60f3ea280cae8b432bf2127d88201d5fc9979bd8471bc29e2
Timestamp: 1706770185 Timestamp [UCT]: 2024-02-01 06:49:45 Age [y:d:h:m:s]: 01:279:15:25:49
Block: 947856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458649 RingCT/type: yes/0
Extra: 013d208871bb8205c60f3ea280cae8b432bf2127d88201d5fc9979bd8471bc29e20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9edda54cc6efa40a3ebbcf4f26fbd5b2c64d07f72dd9d145f4568e1b0f052f74 0.600000000000 1406214 of 15

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": 947866, "vin": [ { "gen": { "height": 947856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9edda54cc6efa40a3ebbcf4f26fbd5b2c64d07f72dd9d145f4568e1b0f052f74" } } ], "extra": [ 1, 61, 32, 136, 113, 187, 130, 5, 198, 15, 62, 162, 128, 202, 232, 180, 50, 191, 33, 39, 216, 130, 1, 213, 252, 153, 121, 189, 132, 113, 188, 41, 226, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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