Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e479066e13e576d19fb2027c75a174bd3e768fa60ab3586ce9a4bdf5f3316d

Tx prefix hash: f809dca0934a5a6722485f1ad3c8b848ead5077046aa397ae89b3e02fd5de4fd
Tx public key: d96c2c98a5a6db5dabb2e0c40ce74465f5944c6a7b0bee4f2bf41f63563edf5b
Timestamp: 1711648502 Timestamp [UCT]: 2024-03-28 17:55:02 Age [y:d:h:m:s]: 00:303:15:34:02
Block: 988339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217284 RingCT/type: yes/0
Extra: 01d96c2c98a5a6db5dabb2e0c40ce74465f5944c6a7b0bee4f2bf41f63563edf5b02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb239f82c9b8697832ce1fbd765430c17ebc4226c5010e0e8e1339e18f96fee 0.600000000000 1448614 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": 988349, "vin": [ { "gen": { "height": 988339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb239f82c9b8697832ce1fbd765430c17ebc4226c5010e0e8e1339e18f96fee" } } ], "extra": [ 1, 217, 108, 44, 152, 165, 166, 219, 93, 171, 178, 224, 196, 12, 231, 68, 101, 245, 148, 76, 106, 123, 11, 238, 79, 43, 244, 31, 99, 86, 62, 223, 91, 2, 17, 0, 0, 0, 8, 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