Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32051befc2c754d162cf222314fb0a200112d4013f52b176304cec478b5190f5

Tx prefix hash: d6140d2fb68b097eb7fb1ab37d2da6e9962bf1c21f56a1c51f7c34afa493784f
Tx public key: 90fb7b94b08b34a660c4533ea69e70bb9985014e45d4e7a45b7d78b1ce6e9147
Timestamp: 1762582644 Timestamp [UCT]: 2025-11-08 06:17:24 Age [y:d:h:m:s]: 00:045:17:49:05
Block: 1407458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32742 RingCT/type: yes/0
Extra: 0190fb7b94b08b34a660c4533ea69e70bb9985014e45d4e7a45b7d78b1ce6e91470211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d47054382f10e33e02477b88a3c3838fcf3d744de0c023a532461f843f4670 0.600000000000 1895879 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": 1407468, "vin": [ { "gen": { "height": 1407458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d47054382f10e33e02477b88a3c3838fcf3d744de0c023a532461f843f4670" } } ], "extra": [ 1, 144, 251, 123, 148, 176, 139, 52, 166, 96, 196, 83, 62, 166, 158, 112, 187, 153, 133, 1, 78, 69, 212, 231, 164, 91, 125, 120, 177, 206, 110, 145, 71, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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