Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee9427753a7f5c66f84a9c7e918b56f73e39a6d5b98402c1761194e2a53444b

Tx prefix hash: 31085c96f1a210c7f5de9e5907aaaad365a0a7dcc962525bcab2662d78723729
Tx public key: 1466ec0955b73b050d09f8683142ce468feee83c5af2f33e8485237f2c1ea755
Timestamp: 1720618516 Timestamp [UCT]: 2024-07-10 13:35:16 Age [y:d:h:m:s]: 00:270:20:06:24
Block: 1062683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193497 RingCT/type: yes/0
Extra: 011466ec0955b73b050d09f8683142ce468feee83c5af2f33e8485237f2c1ea755021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3db338aaaa581f9d7d2c6ea38c86b30de911e1b3aaedb4fb3891e5d03237d567 0.600000000000 1533190 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": 1062693, "vin": [ { "gen": { "height": 1062683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db338aaaa581f9d7d2c6ea38c86b30de911e1b3aaedb4fb3891e5d03237d567" } } ], "extra": [ 1, 20, 102, 236, 9, 85, 183, 59, 5, 13, 9, 248, 104, 49, 66, 206, 70, 143, 238, 232, 60, 90, 242, 243, 62, 132, 133, 35, 127, 44, 30, 167, 85, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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