Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcd44df7c09d6b78cbe6a3e520b16a259558b4c8e2ee413b73eb253042fee151

Tx prefix hash: 36e67be127b056a86c4c5a9630536b545ed7d840d961ac0992c325dc89638d21
Tx public key: 8801202e38868d11b6c4e19cefbb60a5beecb2355c9874c2221e7552af92a010
Timestamp: 1703276322 Timestamp [UCT]: 2023-12-22 20:18:42 Age [y:d:h:m:s]: 01:143:08:16:29
Block: 918911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363594 RingCT/type: yes/0
Extra: 018801202e38868d11b6c4e19cefbb60a5beecb2355c9874c2221e7552af92a01002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31b27089355a652a4ef52238c4cfe45f469c5cb5d5afe95e7074af3b1f27ab5 0.600000000000 1376575 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": 918921, "vin": [ { "gen": { "height": 918911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31b27089355a652a4ef52238c4cfe45f469c5cb5d5afe95e7074af3b1f27ab5" } } ], "extra": [ 1, 136, 1, 32, 46, 56, 134, 141, 17, 182, 196, 225, 156, 239, 187, 96, 165, 190, 236, 178, 53, 92, 152, 116, 194, 34, 30, 117, 82, 175, 146, 160, 16, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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