Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08771fccb04c4a49f9c3e40eca3e6caae56c75489d77c35929cd39700b1e58e1

Tx prefix hash: 79f5a3d1d3216742287f26bea69a5d998a14c35976da4696665c1c39ea7b5fc4
Tx public key: 6e8d60612cfdaf563741c982d93ddf14f2b1d43ab6b182ed0148c46c92869bc1
Timestamp: 1706955003 Timestamp [UCT]: 2024-02-03 10:10:03 Age [y:d:h:m:s]: 01:101:09:02:45
Block: 949388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333559 RingCT/type: yes/0
Extra: 016e8d60612cfdaf563741c982d93ddf14f2b1d43ab6b182ed0148c46c92869bc102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41dc564ac61b0cacb5bf8b266b24129cecb815e34ffcd93d737f9dbc8df14fd1 0.600000000000 1407912 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": 949398, "vin": [ { "gen": { "height": 949388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41dc564ac61b0cacb5bf8b266b24129cecb815e34ffcd93d737f9dbc8df14fd1" } } ], "extra": [ 1, 110, 141, 96, 97, 44, 253, 175, 86, 55, 65, 201, 130, 217, 61, 223, 20, 242, 177, 212, 58, 182, 177, 130, 237, 1, 72, 196, 108, 146, 134, 155, 193, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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