Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d7976cbb0bd88d266be5431f124b0ac33d29595799769d1b89e01795756d25d

Tx prefix hash: 6a76268b0594f8881bbc5ffb3d541715ca03c6f83f2f9a519bb708353273fe71
Tx public key: 4082e2b584ec01f912691a0e5dbc3f11c95029cd72c30135cecea4c2c8d76888
Timestamp: 1634620272 Timestamp [UCT]: 2021-10-19 05:11:12 Age [y:d:h:m:s]: 03:147:10:06:00
Block: 355960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 883244 RingCT/type: yes/0
Extra: 014082e2b584ec01f912691a0e5dbc3f11c95029cd72c30135cecea4c2c8d7688802110000000d8d0de867000000000000000000

1 output(s) for total of 40.602910782000 dcy

stealth address amount amount idx
00: 594ce4b6c57163b6b94ed12c1f25633445f008646fc5be9ce5df90571e0e5f4b 40.602910782000 726486 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": 355970, "vin": [ { "gen": { "height": 355960 } } ], "vout": [ { "amount": 40602910782, "target": { "key": "594ce4b6c57163b6b94ed12c1f25633445f008646fc5be9ce5df90571e0e5f4b" } } ], "extra": [ 1, 64, 130, 226, 181, 132, 236, 1, 249, 18, 105, 26, 14, 93, 188, 63, 17, 201, 80, 41, 205, 114, 195, 1, 53, 206, 206, 164, 194, 200, 215, 104, 136, 2, 17, 0, 0, 0, 13, 141, 13, 232, 103, 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