Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa51a8f00a391c2f1d5ee601e246a26544f54c7a03baa1cf744ad2209603b19e

Tx prefix hash: 2b4f201a4f2a95c8d9d6794f173f2133faba256f91daf83793051e91b3c368b7
Tx public key: 1a703a2cdfdf9354848291f41754b3613bd225e0ee6f5109aead930d3453cfdb
Timestamp: 1737802798 Timestamp [UCT]: 2025-01-25 10:59:58 Age [y:d:h:m:s]: 00:326:01:30:13
Block: 1204956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230611 RingCT/type: yes/0
Extra: 011a703a2cdfdf9354848291f41754b3613bd225e0ee6f5109aead930d3453cfdb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad6a60737558a508d4e8c1856fe68d325a936a45155bc76c7251d2af2c53142b 0.600000000000 1691651 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": 1204966, "vin": [ { "gen": { "height": 1204956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6a60737558a508d4e8c1856fe68d325a936a45155bc76c7251d2af2c53142b" } } ], "extra": [ 1, 26, 112, 58, 44, 223, 223, 147, 84, 132, 130, 145, 244, 23, 84, 179, 97, 59, 210, 37, 224, 238, 111, 81, 9, 174, 173, 147, 13, 52, 83, 207, 219, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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