Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d2452135f95844592a615b2da590490c8546bb70baedd3dc41e49a5ab816782

Tx prefix hash: 114584a2016ee75e8561c1d2b2499fdc3c55c3405f0f77b4c01fd505b9c82533
Tx public key: b1a6194b40cb7ba7d5d4da228263f9f42822e4a48fc887df677ee731b67f4598
Timestamp: 1715123401 Timestamp [UCT]: 2024-05-07 23:10:01 Age [y:d:h:m:s]: 00:232:17:00:41
Block: 1017130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166557 RingCT/type: yes/0
Extra: 01b1a6194b40cb7ba7d5d4da228263f9f42822e4a48fc887df677ee731b67f459802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b35947e4ad8f04f3471ab0066e0cc07abd8cfa082925e551d9f72ee18c55bc0 0.600000000000 1480897 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": 1017140, "vin": [ { "gen": { "height": 1017130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b35947e4ad8f04f3471ab0066e0cc07abd8cfa082925e551d9f72ee18c55bc0" } } ], "extra": [ 1, 177, 166, 25, 75, 64, 203, 123, 167, 213, 212, 218, 34, 130, 99, 249, 244, 40, 34, 228, 164, 143, 200, 135, 223, 103, 126, 231, 49, 182, 127, 69, 152, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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