Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1779f244d80dafcff497cb2c84415c204f37591ae6e2c322d86fc6ce5556ecfb

Tx prefix hash: 86b763a4864fbaed0d549c25f9c53bfadc8f45ebe9a0fdd74246286e00e7fd7e
Tx public key: a4418ffa9894e421e0b1b943f2781b8731b07f062c855cdb037164541e3a2094
Timestamp: 1764906843 Timestamp [UCT]: 2025-12-05 03:54:03 Age [y:d:h:m:s]: 00:018:20:12:26
Block: 1426730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13471 RingCT/type: yes/0
Extra: 01a4418ffa9894e421e0b1b943f2781b8731b07f062c855cdb037164541e3a209402110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2ff78c88241a82522aef8f75303c639525dfb8cb9db1cbc9aac48a1456053f 0.600000000000 1915423 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": 1426740, "vin": [ { "gen": { "height": 1426730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2ff78c88241a82522aef8f75303c639525dfb8cb9db1cbc9aac48a1456053f" } } ], "extra": [ 1, 164, 65, 143, 250, 152, 148, 228, 33, 224, 177, 185, 67, 242, 120, 27, 135, 49, 176, 127, 6, 44, 133, 92, 219, 3, 113, 100, 84, 30, 58, 32, 148, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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