Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bcf95b9f96bc7b094ade5f47dd0ab902f6c8d513da2bcf3262fa974de2bc47e

Tx prefix hash: 0d421401b8a6779ee91cdd1ee087587a41527f71d47e9318f36a9795dde29440
Tx public key: 4d23dce42a0066ecd33498ce9f9ce91b12143a0f2e6347881c4306fe81ccb92b
Timestamp: 1708176924 Timestamp [UCT]: 2024-02-17 13:35:24 Age [y:d:h:m:s]: 01:040:23:41:09
Block: 959534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290317 RingCT/type: yes/0
Extra: 014d23dce42a0066ecd33498ce9f9ce91b12143a0f2e6347881c4306fe81ccb92b02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 881435c743b15ef67ab0bc750b2e7a57de2e2d82721a5eaedee93abbac2d7e6f 0.600000000000 1419071 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": 959544, "vin": [ { "gen": { "height": 959534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "881435c743b15ef67ab0bc750b2e7a57de2e2d82721a5eaedee93abbac2d7e6f" } } ], "extra": [ 1, 77, 35, 220, 228, 42, 0, 102, 236, 211, 52, 152, 206, 159, 156, 233, 27, 18, 20, 58, 15, 46, 99, 71, 136, 28, 67, 6, 254, 129, 204, 185, 43, 2, 17, 0, 0, 0, 10, 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