Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fa7548a7c7e07dc7c00f525d4d8d52c82288dc425429b14b30ade75c12de73d

Tx prefix hash: c25b8cf2884ae57764ebdcd6b01a9706d0abf6fa25e95a6354def4fcbfeaab3a
Tx public key: 5bd0b4b809ce9c4432cf7a298b728c95b30b32506c33d64802155cb669488016
Timestamp: 1711820344 Timestamp [UCT]: 2024-03-30 17:39:04 Age [y:d:h:m:s]: 00:324:08:01:25
Block: 989760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231827 RingCT/type: yes/0
Extra: 015bd0b4b809ce9c4432cf7a298b728c95b30b32506c33d64802155cb6694880160211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe907d54b8acd409f75e675f2a2f3b2446d7b3704835bca7ae6586aa77cd774c 0.600000000000 1450078 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": 989770, "vin": [ { "gen": { "height": 989760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe907d54b8acd409f75e675f2a2f3b2446d7b3704835bca7ae6586aa77cd774c" } } ], "extra": [ 1, 91, 208, 180, 184, 9, 206, 156, 68, 50, 207, 122, 41, 139, 114, 140, 149, 179, 11, 50, 80, 108, 51, 214, 72, 2, 21, 92, 182, 105, 72, 128, 22, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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