Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcda3b0061a42ee97709715740b9bf53115d9f386544b934e7b8e6e71e753178

Tx prefix hash: 81507124828d09663c2d3570dbaef8ae47b1dcb0af81ebdcf2d369ee0fb1cf01
Tx public key: 9af1486b63296caed0fcbdf891f141b21ebc0bf27fdbfbd6b16b77d023728a32
Timestamp: 1746814922 Timestamp [UCT]: 2025-05-09 18:22:02 Age [y:d:h:m:s]: 00:194:14:01:01
Block: 1279335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136779 RingCT/type: yes/0
Extra: 019af1486b63296caed0fcbdf891f141b21ebc0bf27fdbfbd6b16b77d023728a320211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d28bc42953d4c1ad430d75dac681cd19d44ebf958d5e1c46bd8e8e2a9dc2b142 0.600000000000 1766710 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": 1279345, "vin": [ { "gen": { "height": 1279335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d28bc42953d4c1ad430d75dac681cd19d44ebf958d5e1c46bd8e8e2a9dc2b142" } } ], "extra": [ 1, 154, 241, 72, 107, 99, 41, 108, 174, 208, 252, 189, 248, 145, 241, 65, 178, 30, 188, 11, 242, 127, 219, 251, 214, 177, 107, 119, 208, 35, 114, 138, 50, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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