Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec644bc91fd6882489f5faf1b68989bb75203d2fcb9b16ab473e3100100ffb70

Tx prefix hash: 199f8e53fc9f0d0f18127eb80ccd90db9d10bc228412f18e703c3ed67df9699e
Tx public key: 4406e718ee5122d17ea1c9ad2c1ddc7794e2e9c213b92aeddc1a85f8a21248ae
Timestamp: 1705155500 Timestamp [UCT]: 2024-01-13 14:18:20 Age [y:d:h:m:s]: 01:146:17:55:18
Block: 934475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366026 RingCT/type: yes/0
Extra: 014406e718ee5122d17ea1c9ad2c1ddc7794e2e9c213b92aeddc1a85f8a21248ae0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5abf673b5110fdfbf8771587eda35f7a45694817e3bb12171c2c2271ac6222e5 0.600000000000 1392487 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": 934485, "vin": [ { "gen": { "height": 934475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5abf673b5110fdfbf8771587eda35f7a45694817e3bb12171c2c2271ac6222e5" } } ], "extra": [ 1, 68, 6, 231, 24, 238, 81, 34, 209, 126, 161, 201, 173, 44, 29, 220, 119, 148, 226, 233, 194, 19, 185, 42, 237, 220, 26, 133, 248, 162, 18, 72, 174, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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