Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ff94f09bf213e2d238404222e0ce2bfb2f33647604c4b6756531e3395e8c01

Tx prefix hash: f8e726c1cb4d9c15786fc513b4768cb7c2fb7a0861429e236e292f0d7ddc1e0e
Tx public key: d4a5a044c32021155b6783eabfaffa630f37160300e2b684a10bc03c2ac3ae84
Timestamp: 1740471942 Timestamp [UCT]: 2025-02-25 08:25:42 Age [y:d:h:m:s]: 00:269:07:00:47
Block: 1226807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190226 RingCT/type: yes/0
Extra: 01d4a5a044c32021155b6783eabfaffa630f37160300e2b684a10bc03c2ac3ae84021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9148f75c69dbc76dbc3381e653a92d8cc7a914a688448f2b1a857940eb046f9 0.600000000000 1713680 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": 1226817, "vin": [ { "gen": { "height": 1226807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9148f75c69dbc76dbc3381e653a92d8cc7a914a688448f2b1a857940eb046f9" } } ], "extra": [ 1, 212, 165, 160, 68, 195, 32, 33, 21, 91, 103, 131, 234, 191, 175, 250, 99, 15, 55, 22, 3, 0, 226, 182, 132, 161, 11, 192, 60, 42, 195, 174, 132, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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