Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51d0144156b1b63b2ede59c2e2b2c5bc960912a5c7b2b44a1160bd9da4f40e9a

Tx prefix hash: 877e673190206f926a0008fb0f1f5cc95504ac2ffcfd5e6964b54e9d68057e00
Tx public key: 65d585a5d0417248b76957fe7952313e40aaf86fc65c4f007ec40bdf056fbba6
Timestamp: 1700437618 Timestamp [UCT]: 2023-11-19 23:46:58 Age [y:d:h:m:s]: 01:138:21:59:25
Block: 895374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360443 RingCT/type: yes/0
Extra: 0165d585a5d0417248b76957fe7952313e40aaf86fc65c4f007ec40bdf056fbba6021100000003faf35c9c000000000000000000

1 output(s) for total of 0.662604286000 dcy

stealth address amount amount idx
00: 674d1c1616206d26d39344b440b0372e0d2f7a372d8b78b5268c2924994d304a 0.662604286000 1351607 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": 895384, "vin": [ { "gen": { "height": 895374 } } ], "vout": [ { "amount": 662604286, "target": { "key": "674d1c1616206d26d39344b440b0372e0d2f7a372d8b78b5268c2924994d304a" } } ], "extra": [ 1, 101, 213, 133, 165, 208, 65, 114, 72, 183, 105, 87, 254, 121, 82, 49, 62, 64, 170, 248, 111, 198, 92, 79, 0, 126, 196, 11, 223, 5, 111, 187, 166, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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