Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688edf5ea3cad3ce95ccc33ced3b7e4c60a802e5374badfe2fb9f5a83d6e807e

Tx prefix hash: 7ad8e6012a377995d25c777360f1509a076a5d2f3ec2d85d6020cb5e77b359e9
Tx public key: e971d03ae4b660143d1e89685e45c89dabe73476528b477379cbf81b08c52bcc
Timestamp: 1735993483 Timestamp [UCT]: 2025-01-04 12:24:43 Age [y:d:h:m:s]: 00:164:03:49:02
Block: 1190020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117035 RingCT/type: yes/0
Extra: 01e971d03ae4b660143d1e89685e45c89dabe73476528b477379cbf81b08c52bcc02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e56ff7582900e87a18e5115d6fb4f0a036534c4d25f5bfc5a2cdce781ffaff 0.600000000000 1676535 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": 1190030, "vin": [ { "gen": { "height": 1190020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e56ff7582900e87a18e5115d6fb4f0a036534c4d25f5bfc5a2cdce781ffaff" } } ], "extra": [ 1, 233, 113, 208, 58, 228, 182, 96, 20, 61, 30, 137, 104, 94, 69, 200, 157, 171, 231, 52, 118, 82, 139, 71, 115, 121, 203, 248, 27, 8, 197, 43, 204, 2, 17, 0, 0, 0, 1, 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