Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b1a07d00ac50e289a98f59de806db0a01a8042a770f76cc77fa79b3ca58f23

Tx prefix hash: 24be117b00060d0889b0b75c13ea04706f07c83b8087b571b0d42d7808fdeb1d
Tx public key: 4236104ae87b86c18fd8626195f707f130d11a1e411de45d33c45d82e31c0d94
Timestamp: 1727651893 Timestamp [UCT]: 2024-09-29 23:18:13 Age [y:d:h:m:s]: 01:063:00:25:34
Block: 1120997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303456 RingCT/type: yes/0
Extra: 014236104ae87b86c18fd8626195f707f130d11a1e411de45d33c45d82e31c0d9402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb310ae529e5ae3c05403f8ef4b6dd620e9709a86ade6ce9a7b7bc8bf5eebf4 0.600000000000 1603112 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": 1121007, "vin": [ { "gen": { "height": 1120997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb310ae529e5ae3c05403f8ef4b6dd620e9709a86ade6ce9a7b7bc8bf5eebf4" } } ], "extra": [ 1, 66, 54, 16, 74, 232, 123, 134, 193, 143, 216, 98, 97, 149, 247, 7, 241, 48, 209, 26, 30, 65, 29, 228, 93, 51, 196, 93, 130, 227, 28, 13, 148, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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