Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbb8827b4f3e08406a4fae88929a1c553dcdd720a491232f7fb6c0b45783dc2d

Tx prefix hash: 2efdac935a8fa06f1b229ab21b5dcaef9d87bd61d3eaca9086d500c3bc004ca3
Tx public key: c24aa8b8f0418ebe21af9bc6e6b4c1d79526179b8444c1f4971eb53693673f4d
Timestamp: 1751819846 Timestamp [UCT]: 2025-07-06 16:37:26 Age [y:d:h:m:s]: 00:135:01:13:03
Block: 1320039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94933 RingCT/type: yes/0
Extra: 01c24aa8b8f0418ebe21af9bc6e6b4c1d79526179b8444c1f4971eb53693673f4d02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6af797331695a4444cba095e35037f925a17c062eaed71c2f5d7eb3a9da029 0.600000000000 1807734 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": 1320049, "vin": [ { "gen": { "height": 1320039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6af797331695a4444cba095e35037f925a17c062eaed71c2f5d7eb3a9da029" } } ], "extra": [ 1, 194, 74, 168, 184, 240, 65, 142, 190, 33, 175, 155, 198, 230, 180, 193, 215, 149, 38, 23, 155, 132, 68, 193, 244, 151, 30, 181, 54, 147, 103, 63, 77, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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