Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 758c76ade6b4009e938becebecfc05523ff66b2db81d0e5a7ce08eea4113f35a

Tx prefix hash: 5f3be3d0b753d7b95814f545353333f56c0158ec29df90fc5b165932ad7474d0
Tx public key: 4e64ee6c63eac24843a3b979412a374dd430e874e9e705ceeceda3a3ae8c1f57
Timestamp: 1708588612 Timestamp [UCT]: 2024-02-22 07:56:52 Age [y:d:h:m:s]: 01:044:14:30:46
Block: 962947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292892 RingCT/type: yes/0
Extra: 014e64ee6c63eac24843a3b979412a374dd430e874e9e705ceeceda3a3ae8c1f5702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 001ab27072d5010754c7b6fa69caa94633b272cfbe81e4b8fbc0ee34bd185ff9 0.600000000000 1422636 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": 962957, "vin": [ { "gen": { "height": 962947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001ab27072d5010754c7b6fa69caa94633b272cfbe81e4b8fbc0ee34bd185ff9" } } ], "extra": [ 1, 78, 100, 238, 108, 99, 234, 194, 72, 67, 163, 185, 121, 65, 42, 55, 77, 212, 48, 232, 116, 233, 231, 5, 206, 236, 237, 163, 163, 174, 140, 31, 87, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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