Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5db8d3b5c19b6fc1e1d6383ddc858450dac0b97a54ee56fc9d8503e9eb090b6

Tx prefix hash: 8686b0d2d1f75d41893814fc7da8c3512446a4fbdafe20e149495b0bc30e366b
Tx public key: 1de1945cd04b019e80403772e3a97ddc6ed59eabc6f881ffa9d9a528fdb6d360
Timestamp: 1704747812 Timestamp [UCT]: 2024-01-08 21:03:32 Age [y:d:h:m:s]: 01:068:14:18:47
Block: 931088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310157 RingCT/type: yes/0
Extra: 011de1945cd04b019e80403772e3a97ddc6ed59eabc6f881ffa9d9a528fdb6d36002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c5fe9119fdcd33e80ccd4cda48546bf33eda7fbf9b7cc344bd1c2a716c6387 0.600000000000 1388980 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": 931098, "vin": [ { "gen": { "height": 931088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c5fe9119fdcd33e80ccd4cda48546bf33eda7fbf9b7cc344bd1c2a716c6387" } } ], "extra": [ 1, 29, 225, 148, 92, 208, 75, 1, 158, 128, 64, 55, 114, 227, 169, 125, 220, 110, 213, 158, 171, 198, 248, 129, 255, 169, 217, 165, 40, 253, 182, 211, 96, 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