Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59115f0f52e3321df05d7d90d17689e3ca1e882e95022a4c89746871fa69dd76

Tx prefix hash: a468eb4b19c0ef96e4c32ff93b1ce52e1b310e9f0189a447045e0332a486b8cd
Tx public key: f8c1c0838d07fa7cb75dae8033b1fe71ccafbc400378a4717ab08dbb1dc7d377
Timestamp: 1724164081 Timestamp [UCT]: 2024-08-20 14:28:01 Age [y:d:h:m:s]: 00:240:16:54:15
Block: 1092081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171908 RingCT/type: yes/0
Extra: 01f8c1c0838d07fa7cb75dae8033b1fe71ccafbc400378a4717ab08dbb1dc7d377021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e69a44cdd0409c4bf8a912232a01f85e6796cee3ce511b4bb5b417261eae160 0.600000000000 1566758 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": 1092091, "vin": [ { "gen": { "height": 1092081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e69a44cdd0409c4bf8a912232a01f85e6796cee3ce511b4bb5b417261eae160" } } ], "extra": [ 1, 248, 193, 192, 131, 141, 7, 250, 124, 183, 93, 174, 128, 51, 177, 254, 113, 204, 175, 188, 64, 3, 120, 164, 113, 122, 176, 141, 187, 29, 199, 211, 119, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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