Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68c788acb31978e989dd356c490b0c3e4003cb1540ba385659817437dc207c3f

Tx prefix hash: 0dcfcc5bcee3589f02b1bfc1957bdb1c0a9be39bbffd92f1e94e8b354a06c1e5
Tx public key: 1ea4c951afae348f95e11007d732082646387511fafd26b5e93ee8a0a9abbaf5
Timestamp: 1710215774 Timestamp [UCT]: 2024-03-12 03:56:14 Age [y:d:h:m:s]: 01:011:08:07:39
Block: 976453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269086 RingCT/type: yes/0
Extra: 011ea4c951afae348f95e11007d732082646387511fafd26b5e93ee8a0a9abbaf50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf49c15d906eaea18ff769f7f1a0356621fdc789fa71b11126b6afa99de29d02 0.600000000000 1436448 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": 976463, "vin": [ { "gen": { "height": 976453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf49c15d906eaea18ff769f7f1a0356621fdc789fa71b11126b6afa99de29d02" } } ], "extra": [ 1, 30, 164, 201, 81, 175, 174, 52, 143, 149, 225, 16, 7, 215, 50, 8, 38, 70, 56, 117, 17, 250, 253, 38, 181, 233, 62, 232, 160, 169, 171, 186, 245, 2, 17, 0, 0, 0, 4, 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