Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d21c09e3c3ad52bfae482ca2ac82ad3dc7d083ec44fa0be02c296ad28a56266a

Tx prefix hash: 249437093e90c32d2c991748ca385273c038eadee3bbef308c0dec4352b0ac6c
Tx public key: fe0dd886645d8a73a83ba5aeadc311ba1e6fb48a6ae63a332f6365b1d3ed810c
Timestamp: 1726499210 Timestamp [UCT]: 2024-09-16 15:06:50 Age [y:d:h:m:s]: 00:213:17:32:10
Block: 1111443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152583 RingCT/type: yes/0
Extra: 01fe0dd886645d8a73a83ba5aeadc311ba1e6fb48a6ae63a332f6365b1d3ed810c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a58839295117b17a884c13568d1d1a38335278573382b11fbd175721201afb 0.600000000000 1590400 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": 1111453, "vin": [ { "gen": { "height": 1111443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a58839295117b17a884c13568d1d1a38335278573382b11fbd175721201afb" } } ], "extra": [ 1, 254, 13, 216, 134, 100, 93, 138, 115, 168, 59, 165, 174, 173, 195, 17, 186, 30, 111, 180, 138, 106, 230, 58, 51, 47, 99, 101, 177, 211, 237, 129, 12, 2, 17, 0, 0, 0, 3, 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