Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8270328c23b574082546b7eedecf49ed2ec3606edd8bfc09bec7c155da9d5d

Tx prefix hash: de53c10dd13308a89c44f80ea43f28d3f3128dafd2d761fb6a9db0392fa0dcb9
Tx public key: b6e297f048cda82f7b9594939b4a0223f06f03582940db00cdb1d5e97a8425c3
Timestamp: 1756520627 Timestamp [UCT]: 2025-08-30 02:23:47 Age [y:d:h:m:s]: 00:115:15:16:03
Block: 1357379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82633 RingCT/type: yes/0
Extra: 01b6e297f048cda82f7b9594939b4a0223f06f03582940db00cdb1d5e97a8425c302110000000ead7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac72a37506386db21d9ce9ae7bd494d3780465b03a58de8283fbd13ea470f7f8 0.600000000000 1845388 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": 1357389, "vin": [ { "gen": { "height": 1357379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac72a37506386db21d9ce9ae7bd494d3780465b03a58de8283fbd13ea470f7f8" } } ], "extra": [ 1, 182, 226, 151, 240, 72, 205, 168, 47, 123, 149, 148, 147, 155, 74, 2, 35, 240, 111, 3, 88, 41, 64, 219, 0, 205, 177, 213, 233, 122, 132, 37, 195, 2, 17, 0, 0, 0, 14, 173, 121, 72, 208, 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