Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b09852c813da501666cea638d5aab1feaba1a8dad188d7ab6304df030e831a8d

Tx prefix hash: 14abd3eb0f49fc319e37729a6ce617aa9fa0596bee4602d5f0615b76061c81df
Tx public key: 671a1e651d27106ce7482b02a63a7198d8db208da0bb61bc5a272ac00f000cd3
Timestamp: 1702081306 Timestamp [UCT]: 2023-12-09 00:21:46 Age [y:d:h:m:s]: 01:115:17:41:45
Block: 908996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343862 RingCT/type: yes/0
Extra: 01671a1e651d27106ce7482b02a63a7198d8db208da0bb61bc5a272ac00f000cd302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a68a6c118c0fdcf8f7b770dc6dc282b13a1f19f921155a10ce0c6fbbff1b725 0.600000000000 1366061 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": 909006, "vin": [ { "gen": { "height": 908996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a68a6c118c0fdcf8f7b770dc6dc282b13a1f19f921155a10ce0c6fbbff1b725" } } ], "extra": [ 1, 103, 26, 30, 101, 29, 39, 16, 108, 231, 72, 43, 2, 166, 58, 113, 152, 216, 219, 32, 141, 160, 187, 97, 188, 90, 39, 42, 192, 15, 0, 12, 211, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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