Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6661054a9984ae92749cd5cab75fa5dd42587587459fbd0323c4395b186a0ae4

Tx prefix hash: 21df8454a88d97c2d02d228f89c479e7e478ea7f9664a0a68cb9a098120a7c6a
Tx public key: d85089c86abc5a52756e5e7623a99369bab6e07fe5d095b2d1bdf2d903fc9544
Timestamp: 1709704415 Timestamp [UCT]: 2024-03-06 05:53:35 Age [y:d:h:m:s]: 01:075:05:43:03
Block: 972212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314792 RingCT/type: yes/0
Extra: 01d85089c86abc5a52756e5e7623a99369bab6e07fe5d095b2d1bdf2d903fc954402110000000446812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a610568a086539d3982ec74fcb90bf2feec864a6a0c4e6940f52c76ccba9e9 0.600000000000 1432119 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": 972222, "vin": [ { "gen": { "height": 972212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a610568a086539d3982ec74fcb90bf2feec864a6a0c4e6940f52c76ccba9e9" } } ], "extra": [ 1, 216, 80, 137, 200, 106, 188, 90, 82, 117, 110, 94, 118, 35, 169, 147, 105, 186, 182, 224, 127, 229, 208, 149, 178, 209, 189, 242, 217, 3, 252, 149, 68, 2, 17, 0, 0, 0, 4, 70, 129, 43, 184, 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