Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aafea94323de69a7028f63299962a88184c4d2f649b73ac3fbbc1bdada46d7f

Tx prefix hash: fccb7f6a910848734ab79404ce58b235a56fef8833b1c0f06bda048e6ae2d89b
Tx public key: 069f82635ffb862532f091f6af6fba04d1240ef940b594224da7ab39be022a24
Timestamp: 1704987927 Timestamp [UCT]: 2024-01-11 15:45:27 Age [y:d:h:m:s]: 01:309:03:13:32
Block: 933090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479764 RingCT/type: yes/0
Extra: 01069f82635ffb862532f091f6af6fba04d1240ef940b594224da7ab39be022a2402110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e928c1606c342b98ad1d53169f6c5769ea6808e5810a52b272c795b29d33da03 0.600000000000 1391042 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": 933100, "vin": [ { "gen": { "height": 933090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e928c1606c342b98ad1d53169f6c5769ea6808e5810a52b272c795b29d33da03" } } ], "extra": [ 1, 6, 159, 130, 99, 95, 251, 134, 37, 50, 240, 145, 246, 175, 111, 186, 4, 209, 36, 14, 249, 64, 181, 148, 34, 77, 167, 171, 57, 190, 2, 42, 36, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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