Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5bce1fd6004952d2dc78cb982608de303118fe272e6a7019d9584bfdb5ef9b2

Tx prefix hash: ba8860c0918019f861735e3f1ebcdf48c5daf544eb87cad4e67b5a7756d5e131
Tx public key: 33e4425d2c36bf4d63eb750b0dfe5d7aa3bba9e46170acde8a3a43251567815d
Timestamp: 1737732784 Timestamp [UCT]: 2025-01-24 15:33:04 Age [y:d:h:m:s]: 00:144:07:28:26
Block: 1204369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102877 RingCT/type: yes/0
Extra: 0133e4425d2c36bf4d63eb750b0dfe5d7aa3bba9e46170acde8a3a43251567815d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57bded3faaf1ec894125f2a0f6ee2d0532fc81ca19601ed5bbbdd6ef1e5c5c4d 0.600000000000 1691054 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": 1204379, "vin": [ { "gen": { "height": 1204369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57bded3faaf1ec894125f2a0f6ee2d0532fc81ca19601ed5bbbdd6ef1e5c5c4d" } } ], "extra": [ 1, 51, 228, 66, 93, 44, 54, 191, 77, 99, 235, 117, 11, 13, 254, 93, 122, 163, 187, 169, 228, 97, 112, 172, 222, 138, 58, 67, 37, 21, 103, 129, 93, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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