Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439b4d0acddcc8571def59e560a64c44e31c45a398ed088a5d9dd824b5ae36cc

Tx prefix hash: b20c250acb0611aeceeec9dd95a90064c338d6e8669e9d9fdfe0f434bbfdfce7
Tx public key: 73963d64eb1b2f61ff2800efa58ef257fe9e8c66af310add659ecf6a7de257cd
Timestamp: 1715409309 Timestamp [UCT]: 2024-05-11 06:35:09 Age [y:d:h:m:s]: 00:327:13:54:14
Block: 1019523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234117 RingCT/type: yes/0
Extra: 0173963d64eb1b2f61ff2800efa58ef257fe9e8c66af310add659ecf6a7de257cd021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c25a1e26f3654a8f4b0c3455baa6940eb78133fad8fca03031cfe2adc6efaa4 0.600000000000 1483512 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": 1019533, "vin": [ { "gen": { "height": 1019523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c25a1e26f3654a8f4b0c3455baa6940eb78133fad8fca03031cfe2adc6efaa4" } } ], "extra": [ 1, 115, 150, 61, 100, 235, 27, 47, 97, 255, 40, 0, 239, 165, 142, 242, 87, 254, 158, 140, 102, 175, 49, 10, 221, 101, 158, 207, 106, 125, 226, 87, 205, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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