Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 312199e6bc19b690ce0f64e948a8f2669de2a3ed0bfab2129b22f9e00019d8c5

Tx prefix hash: 34518984def2adf6915ee4eecedebcb0021585a10146ef4ad99b35faabb35d3d
Tx public key: aa5b5ae2837811c368f03c1ebbb2f2e9d8c5b3010d02e36d31a56d5b914019b0
Timestamp: 1756159911 Timestamp [UCT]: 2025-08-25 22:11:51 Age [y:d:h:m:s]: 00:131:01:28:50
Block: 1354415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93670 RingCT/type: yes/0
Extra: 01aa5b5ae2837811c368f03c1ebbb2f2e9d8c5b3010d02e36d31a56d5b914019b00211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 191222efc90df7334ead78cec4b577134aecd2ed8c23524ed49f8041be298c3b 0.600000000000 1842404 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": 1354425, "vin": [ { "gen": { "height": 1354415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "191222efc90df7334ead78cec4b577134aecd2ed8c23524ed49f8041be298c3b" } } ], "extra": [ 1, 170, 91, 90, 226, 131, 120, 17, 195, 104, 240, 60, 30, 187, 178, 242, 233, 216, 197, 179, 1, 13, 2, 227, 109, 49, 165, 109, 91, 145, 64, 25, 176, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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