Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dfff6a66778891e0373c4ffe315e4bbbc0272323a661ca8fdadc6900fa08387

Tx prefix hash: 0d546af190de241fc1372f9e0c73e990f644863a99c278b6d3dc2874899324ad
Tx public key: 686c7682d5748dd9f7e1d43c1a1ef27b21bc0b867cb7ea820b204f970d6f9f6c
Timestamp: 1703057028 Timestamp [UCT]: 2023-12-20 07:23:48 Age [y:d:h:m:s]: 01:090:04:00:12
Block: 917088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325583 RingCT/type: yes/0
Extra: 01686c7682d5748dd9f7e1d43c1a1ef27b21bc0b867cb7ea820b204f970d6f9f6c021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30fce6005bc66bcc970f54710e76b5a110d385a9d253739bbb8f48d8799467e4 0.600000000000 1374652 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": 917098, "vin": [ { "gen": { "height": 917088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30fce6005bc66bcc970f54710e76b5a110d385a9d253739bbb8f48d8799467e4" } } ], "extra": [ 1, 104, 108, 118, 130, 213, 116, 141, 217, 247, 225, 212, 60, 26, 30, 242, 123, 33, 188, 11, 134, 124, 183, 234, 130, 11, 32, 79, 151, 13, 111, 159, 108, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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