Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74470ab8874dab962440c5b7f486a115866ef8db2748ad61d9185d8f62afa9e8

Tx prefix hash: 7a1048168d7de506fbe8fbf11d80168e4dacf7b8de9002c2a17ebc298ae32c79
Tx public key: 792c05df057121f3f9a2cf041ffc9a24a1ef09867880e0267f091ef57b2499e8
Timestamp: 1707134131 Timestamp [UCT]: 2024-02-05 11:55:31 Age [y:d:h:m:s]: 00:343:22:46:12
Block: 950876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246238 RingCT/type: yes/0
Extra: 01792c05df057121f3f9a2cf041ffc9a24a1ef09867880e0267f091ef57b2499e80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5396e2d5f5338eea7a804f53b905e91aa5267a60762d650c830d069bd20331c 0.600000000000 1409564 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": 950886, "vin": [ { "gen": { "height": 950876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5396e2d5f5338eea7a804f53b905e91aa5267a60762d650c830d069bd20331c" } } ], "extra": [ 1, 121, 44, 5, 223, 5, 113, 33, 243, 249, 162, 207, 4, 31, 252, 154, 36, 161, 239, 9, 134, 120, 128, 224, 38, 127, 9, 30, 245, 123, 36, 153, 232, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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