Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339129d5f1bc18682641f9e18dd9aa8f00188bd0343634d49d94fe78c0141507

Tx prefix hash: 1b3f5990e1f3ccf2c73e12014ffef281022c1273af98e31b6dd2f76f9134f143
Tx public key: a4f535241fd04a55ad7f5b6feac6daa65baed6d2782a1d834b45e741e8daa26b
Timestamp: 1763066293 Timestamp [UCT]: 2025-11-13 20:38:13 Age [y:d:h:m:s]: 00:053:03:14:06
Block: 1411469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38065 RingCT/type: yes/0
Extra: 01a4f535241fd04a55ad7f5b6feac6daa65baed6d2782a1d834b45e741e8daa26b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 077d699bac9230bc8d694a864e9ef4991ac59610f13af7e2e08b4222c39b1723 0.600000000000 1899930 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": 1411479, "vin": [ { "gen": { "height": 1411469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "077d699bac9230bc8d694a864e9ef4991ac59610f13af7e2e08b4222c39b1723" } } ], "extra": [ 1, 164, 245, 53, 36, 31, 208, 74, 85, 173, 127, 91, 111, 234, 198, 218, 166, 91, 174, 214, 210, 120, 42, 29, 131, 75, 69, 231, 65, 232, 218, 162, 107, 2, 17, 0, 0, 0, 2, 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