Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530bd9f1043a794eb1e675e4c0e5c7c50df49fc8ca76623b56aee967c331feed

Tx prefix hash: 221821c7e1064b58be66f14ddb7e65d565387b5e5a4ddf0a8fbf7c5004ec2faf
Tx public key: ff7aa1971fc331dafd0f592193483821ef8073d2b89cae1f7b1af39fafa593fe
Timestamp: 1709133333 Timestamp [UCT]: 2024-02-28 15:15:33 Age [y:d:h:m:s]: 00:259:17:34:39
Block: 967473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185941 RingCT/type: yes/0
Extra: 01ff7aa1971fc331dafd0f592193483821ef8073d2b89cae1f7b1af39fafa593fe0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d84cb47b9e668097d501e169f13c14f8fbda5e836e5cdaa8cab25db25aa71cb0 0.600000000000 1427252 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": 967483, "vin": [ { "gen": { "height": 967473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d84cb47b9e668097d501e169f13c14f8fbda5e836e5cdaa8cab25db25aa71cb0" } } ], "extra": [ 1, 255, 122, 161, 151, 31, 195, 49, 218, 253, 15, 89, 33, 147, 72, 56, 33, 239, 128, 115, 210, 184, 156, 174, 31, 123, 26, 243, 159, 175, 165, 147, 254, 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