Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ae25c95a1e540b138cfd7c2286b76030c8894f92a0d8e01a558ab418b808b89

Tx prefix hash: 89fec2819889ffa6a113d05a99ed27ee9f7943d458768cc237e5d761a4c839c1
Tx public key: fe691c72a925887d918c136d9e0ca12d86b9f404ce277656ad6930d629461a48
Timestamp: 1736575270 Timestamp [UCT]: 2025-01-11 06:01:10 Age [y:d:h:m:s]: 00:159:16:51:31
Block: 1194836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113821 RingCT/type: yes/0
Extra: 01fe691c72a925887d918c136d9e0ca12d86b9f404ce277656ad6930d629461a48021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 431c56fbef17f1c4ff12c0d020eef95ffecacd7363e8dfcacf9b28f1d129aac6 0.600000000000 1681413 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": 1194846, "vin": [ { "gen": { "height": 1194836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "431c56fbef17f1c4ff12c0d020eef95ffecacd7363e8dfcacf9b28f1d129aac6" } } ], "extra": [ 1, 254, 105, 28, 114, 169, 37, 136, 125, 145, 140, 19, 109, 158, 12, 161, 45, 134, 185, 244, 4, 206, 39, 118, 86, 173, 105, 48, 214, 41, 70, 26, 72, 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