Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39031ca58a2c6cac7ec58482e1061fceb00d38791956b4c5ff4fc9d3b04d9ae7

Tx prefix hash: f923367420302af27b10dd0d65d2c64c089bc40a538d8face0bb39941625ea7f
Tx public key: 2dcbcf7ee97806a426654b4fdf170ab1649363ae3bf769ae3c4cdb38da8ce352
Timestamp: 1761680492 Timestamp [UCT]: 2025-10-28 19:41:32 Age [y:d:h:m:s]: 00:009:06:01:57
Block: 1399996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6606 RingCT/type: yes/0
Extra: 012dcbcf7ee97806a426654b4fdf170ab1649363ae3bf769ae3c4cdb38da8ce35202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6986cafa93604e21564f223c0e9a79fe8f57232b7026ac2eb4ca51364e9d52e 0.600000000000 1888303 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": 1400006, "vin": [ { "gen": { "height": 1399996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6986cafa93604e21564f223c0e9a79fe8f57232b7026ac2eb4ca51364e9d52e" } } ], "extra": [ 1, 45, 203, 207, 126, 233, 120, 6, 164, 38, 101, 75, 79, 223, 23, 10, 177, 100, 147, 99, 174, 59, 247, 105, 174, 60, 76, 219, 56, 218, 140, 227, 82, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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