Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd08b3140c6028e5cc03ba05332157ef6ba34393e29e8a5621c8c59d494ea71f

Tx prefix hash: ef6a8064772c0802eacd17a8cba42859a4e12eec1912d6bead31edd35d34c481
Tx public key: 45f82fda7a0f6a6e45d73f9f497a8e7d52377432840af62edf356f20c7c3fdc9
Timestamp: 1750969788 Timestamp [UCT]: 2025-06-26 20:29:48 Age [y:d:h:m:s]: 00:147:01:31:48
Block: 1313401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103117 RingCT/type: yes/0
Extra: 0145f82fda7a0f6a6e45d73f9f497a8e7d52377432840af62edf356f20c7c3fdc902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65321f116cb7e4923fadc0a280eec2decfc1bb8787d410d7526c5045d6b281d 0.600000000000 1801040 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": 1313411, "vin": [ { "gen": { "height": 1313401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65321f116cb7e4923fadc0a280eec2decfc1bb8787d410d7526c5045d6b281d" } } ], "extra": [ 1, 69, 248, 47, 218, 122, 15, 106, 110, 69, 215, 63, 159, 73, 122, 142, 125, 82, 55, 116, 50, 132, 10, 246, 46, 223, 53, 111, 32, 199, 195, 253, 201, 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