Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71eb733b5e5cc03da35440174daec0fc92ba3db769424cebcf7424cb343a410f

Tx prefix hash: 0dd810fd5ddc9cde9b76a352c78c73e39ef6d299d447cf983003a09fa2ba2a28
Tx public key: 21fd60dae7c6bb52f31c72a45f9403604ec226183f8058d3ba5e9da49786bb67
Timestamp: 1580703167 Timestamp [UCT]: 2020-02-03 04:12:47 Age [y:d:h:m:s]: 04:298:06:11:55
Block: 57723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104325 RingCT/type: yes/0
Extra: 0121fd60dae7c6bb52f31c72a45f9403604ec226183f8058d3ba5e9da49786bb67021100000002ff58ae94000000000000000000

1 output(s) for total of 395.130506077000 dcy

stealth address amount amount idx
00: 1b3318c52edca5ff96e2d229d05eb286016a83ead9d7a36824e83bd90e95a7db 395.130506077000 106670 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": 57733, "vin": [ { "gen": { "height": 57723 } } ], "vout": [ { "amount": 395130506077, "target": { "key": "1b3318c52edca5ff96e2d229d05eb286016a83ead9d7a36824e83bd90e95a7db" } } ], "extra": [ 1, 33, 253, 96, 218, 231, 198, 187, 82, 243, 28, 114, 164, 95, 148, 3, 96, 78, 194, 38, 24, 63, 128, 88, 211, 186, 94, 157, 164, 151, 134, 187, 103, 2, 17, 0, 0, 0, 2, 255, 88, 174, 148, 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