Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258d0251c24616f91d54e8f4cf8677509855ff39908bfd4577277ec4430eab45

Tx prefix hash: d2f2cbd7e340523e21c96cd7a4944fda9c3a7be4eb014795fbc7836dbb3b97cf
Tx public key: 338441e846a4cac77ae946cc5ca98dadba7d216b5164c1ec120b5a3b1b9be141
Timestamp: 1738387234 Timestamp [UCT]: 2025-02-01 05:20:34 Age [y:d:h:m:s]: 00:290:03:57:05
Block: 1209563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205151 RingCT/type: yes/0
Extra: 01338441e846a4cac77ae946cc5ca98dadba7d216b5164c1ec120b5a3b1b9be14102110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cea99529ddb6f71282a1e0c3680eb852c7434e23fd1b3805f35c2833b817559 0.600000000000 1696308 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": 1209573, "vin": [ { "gen": { "height": 1209563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cea99529ddb6f71282a1e0c3680eb852c7434e23fd1b3805f35c2833b817559" } } ], "extra": [ 1, 51, 132, 65, 232, 70, 164, 202, 199, 122, 233, 70, 204, 92, 169, 141, 173, 186, 125, 33, 107, 81, 100, 193, 236, 18, 11, 90, 59, 27, 155, 225, 65, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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