Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381ed6a044f817beef0d6ebda4bead2769bdcbfa1aa1c1409cb0d167b594944a

Tx prefix hash: ab726e2a0845f191493e7383f5efc63e0b9207c132e561b7db343584bbeff75c
Tx public key: a5b35e7aef497e1f41e870312c857b47e92d06e28eef73b15bb8b6c47ad9925d
Timestamp: 1742528614 Timestamp [UCT]: 2025-03-21 03:43:34 Age [y:d:h:m:s]: 00:201:23:53:42
Block: 1243871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142033 RingCT/type: yes/0
Extra: 01a5b35e7aef497e1f41e870312c857b47e92d06e28eef73b15bb8b6c47ad9925d021100000001bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737c391fb6758e766dd6aa14c18d20e41691ee80076a3fbade570c572ba91e2b 0.600000000000 1730862 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": 1243881, "vin": [ { "gen": { "height": 1243871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737c391fb6758e766dd6aa14c18d20e41691ee80076a3fbade570c572ba91e2b" } } ], "extra": [ 1, 165, 179, 94, 122, 239, 73, 126, 31, 65, 232, 112, 49, 44, 133, 123, 71, 233, 45, 6, 226, 142, 239, 115, 177, 91, 184, 182, 196, 122, 217, 146, 93, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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