Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35486dd0257cd242dec8fbedfda5c8056f4a71ee2cba8776b78411a5bb4cc7b9

Tx prefix hash: 22eddd6c5700bbab26a42bf78d14a161e067d2747f438cd9f6f8f8a79c64e276
Tx public key: 59f789e8683d33eea60a9222b2a4d13565a0f108cb4736f14b4779225c2f1b76
Timestamp: 1720319404 Timestamp [UCT]: 2024-07-07 02:30:04 Age [y:d:h:m:s]: 00:277:01:03:05
Block: 1060201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197950 RingCT/type: yes/0
Extra: 0159f789e8683d33eea60a9222b2a4d13565a0f108cb4736f14b4779225c2f1b7602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d7aa9589d79a73775debe28f7c8c11730c29d5dcd9c60bc0843f9406c14cd90 0.600000000000 1530672 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": 1060211, "vin": [ { "gen": { "height": 1060201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d7aa9589d79a73775debe28f7c8c11730c29d5dcd9c60bc0843f9406c14cd90" } } ], "extra": [ 1, 89, 247, 137, 232, 104, 61, 51, 238, 166, 10, 146, 34, 178, 164, 209, 53, 101, 160, 241, 8, 203, 71, 54, 241, 75, 71, 121, 34, 92, 47, 27, 118, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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