Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a6eaf529c77128cbb159635e71959394132dc0e2fbe9c8761ad75a1b2a2ffe

Tx prefix hash: b561804015926c8eedf1a5be3a337b1daae10aa4dd76408239f4b01c8a846884
Tx public key: 8df2d060d2a66b59f2ba6a9918e6645caa7c18f4150314da70f9810238b0bb47
Timestamp: 1764611639 Timestamp [UCT]: 2025-12-01 17:53:59 Age [y:d:h:m:s]: 00:035:05:42:52
Block: 1424278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25253 RingCT/type: yes/0
Extra: 018df2d060d2a66b59f2ba6a9918e6645caa7c18f4150314da70f9810238b0bb4702110000000fd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90c5e61ab58cb641fff8da36cad529bb9725f9e89714a2fac7920fe86d78dce5 0.600000000000 1912909 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": 1424288, "vin": [ { "gen": { "height": 1424278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90c5e61ab58cb641fff8da36cad529bb9725f9e89714a2fac7920fe86d78dce5" } } ], "extra": [ 1, 141, 242, 208, 96, 210, 166, 107, 89, 242, 186, 106, 153, 24, 230, 100, 92, 170, 124, 24, 244, 21, 3, 20, 218, 112, 249, 129, 2, 56, 176, 187, 71, 2, 17, 0, 0, 0, 15, 214, 225, 157, 124, 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