Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 857bb6b3fab4fdbb3eb01568fe5c555c3fc0953516035892a7ecb1032fc4bd21

Tx prefix hash: c1f5237b6ecd745f31710df6d7611225e38238566ef50c909342d50d5410c11d
Tx public key: 3be7aaae4f5b5b371478cf3ed7d4246f338ad7060c851dfdee5ba1115bc3e9fa
Timestamp: 1753227369 Timestamp [UCT]: 2025-07-22 23:36:09 Age [y:d:h:m:s]: 00:121:14:32:29
Block: 1331285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85710 RingCT/type: yes/0
Extra: 013be7aaae4f5b5b371478cf3ed7d4246f338ad7060c851dfdee5ba1115bc3e9fa0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52cf01b78a7c4320a29aa16d0cca61421e36df62d8c748df212aa1712a6d6dbf 0.600000000000 1819080 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": 1331295, "vin": [ { "gen": { "height": 1331285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52cf01b78a7c4320a29aa16d0cca61421e36df62d8c748df212aa1712a6d6dbf" } } ], "extra": [ 1, 59, 231, 170, 174, 79, 91, 91, 55, 20, 120, 207, 62, 215, 212, 36, 111, 51, 138, 215, 6, 12, 133, 29, 253, 238, 91, 161, 17, 91, 195, 233, 250, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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