Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5370f15620da64f0cf3f69df8b364cad873f93e6fd7abf1df4b5f0c08dda3d91

Tx prefix hash: fe0fe1f43e156a8a125df05127b702a2232bbf92d24a316d7d175459748c1a1a
Tx public key: 6767ece558d40c20e6b1d2ecd7399f47d993e8c44db216e60edd96fb01662c0d
Timestamp: 1706138854 Timestamp [UCT]: 2024-01-24 23:27:34 Age [y:d:h:m:s]: 01:293:17:14:51
Block: 942612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468741 RingCT/type: yes/0
Extra: 016767ece558d40c20e6b1d2ecd7399f47d993e8c44db216e60edd96fb01662c0d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35ed17fcfbfbfb65502e0f97b22ff681f1b2805d2801ff96b900eee4e30ede52 0.600000000000 1400786 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": 942622, "vin": [ { "gen": { "height": 942612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35ed17fcfbfbfb65502e0f97b22ff681f1b2805d2801ff96b900eee4e30ede52" } } ], "extra": [ 1, 103, 103, 236, 229, 88, 212, 12, 32, 230, 177, 210, 236, 215, 57, 159, 71, 217, 147, 232, 196, 77, 178, 22, 230, 14, 221, 150, 251, 1, 102, 44, 13, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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