Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40020e5d929d3cf9ed0ab237eb1b29365b6963915ccaf2da443c1c9d4f47735b

Tx prefix hash: 1bb4ce557ac8557f958d95e9e57d3332361161031cf82140bc2c3a738e20f631
Tx public key: f66a896489a18d08ee3002ba11b4f6249aa10f12b3bf76053d32516bcc36f5df
Timestamp: 1751859007 Timestamp [UCT]: 2025-07-07 03:30:07 Age [y:d:h:m:s]: 00:130:07:15:34
Block: 1320352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91540 RingCT/type: yes/0
Extra: 01f66a896489a18d08ee3002ba11b4f6249aa10f12b3bf76053d32516bcc36f5df021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f2a8f11ed94e012e36afe5f1efde18193aba48515ec0f20db3f7e2e4ed2b3b 0.600000000000 1808049 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": 1320362, "vin": [ { "gen": { "height": 1320352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f2a8f11ed94e012e36afe5f1efde18193aba48515ec0f20db3f7e2e4ed2b3b" } } ], "extra": [ 1, 246, 106, 137, 100, 137, 161, 141, 8, 238, 48, 2, 186, 17, 180, 246, 36, 154, 161, 15, 18, 179, 191, 118, 5, 61, 50, 81, 107, 204, 54, 245, 223, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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