Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7358b49b23cb966d7fd0ffd7b4cdcef51927144c0ffaeb0431768aabc601dd6

Tx prefix hash: f8984a697c507e5195c68df945142398585190326c95ffd044d68fd0132eb158
Tx public key: 8f548eda9e9b6e12650fe9c8bc1d73285d1f676dbb18bf0c6a45cf8a27b2a55a
Timestamp: 1731219101 Timestamp [UCT]: 2024-11-10 06:11:41 Age [y:d:h:m:s]: 00:217:20:40:34
Block: 1150483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155485 RingCT/type: yes/0
Extra: 018f548eda9e9b6e12650fe9c8bc1d73285d1f676dbb18bf0c6a45cf8a27b2a55a021100000005007f978a000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: a7d9d93ea46316f924eef2906ac4c95bdfcb6e0efccc243e595bbd969fdaa190 0.608000000000 1635808 of 0

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": 1150493, "vin": [ { "gen": { "height": 1150483 } } ], "vout": [ { "amount": 608000000, "target": { "key": "a7d9d93ea46316f924eef2906ac4c95bdfcb6e0efccc243e595bbd969fdaa190" } } ], "extra": [ 1, 143, 84, 142, 218, 158, 155, 110, 18, 101, 15, 233, 200, 188, 29, 115, 40, 93, 31, 103, 109, 187, 24, 191, 12, 106, 69, 207, 138, 39, 178, 165, 90, 2, 17, 0, 0, 0, 5, 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