Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569a7829ec6e0b0d2d663a3a79a2f5701787fa5475bfe745a61c0f89e48cd801

Tx prefix hash: 1d72d9fa9fec463ec30c57986c7dbdb8ad462ec87a15e2280537bd4e6ef2b968
Tx public key: ba874511453a4a7a098c85aa3ae4aaea1db11f0747f44b94292d86773bf03a7e
Timestamp: 1633728653 Timestamp [UCT]: 2021-10-08 21:30:53 Age [y:d:h:m:s]: 03:028:15:18:07
Block: 349384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797705 RingCT/type: yes/0
Extra: 01ba874511453a4a7a098c85aa3ae4aaea1db11f0747f44b94292d86773bf03a7e021100000006f60c5d7e000000000000000000

1 output(s) for total of 42.694660007000 dcy

stealth address amount amount idx
00: 37e669245072c0ebd37fd9bd71d4217f45c89e0c98a936a8ab67062962e28cf7 42.694660007000 715341 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": 349394, "vin": [ { "gen": { "height": 349384 } } ], "vout": [ { "amount": 42694660007, "target": { "key": "37e669245072c0ebd37fd9bd71d4217f45c89e0c98a936a8ab67062962e28cf7" } } ], "extra": [ 1, 186, 135, 69, 17, 69, 58, 74, 122, 9, 140, 133, 170, 58, 228, 170, 234, 29, 177, 31, 7, 71, 244, 75, 148, 41, 45, 134, 119, 59, 240, 58, 126, 2, 17, 0, 0, 0, 6, 246, 12, 93, 126, 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