Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e5434c6af10134925da2d6c30f4eac7c1ca2e09868300886e0f1893032d62ec

Tx prefix hash: 6ceeed91c03097ea9b48f35ae21bd157f9f6d6560374becc224b9e4ce52c5403
Tx public key: a61580986db4f2ae88034d2d9511fbd4b52fa361f224ea4b5b7aefa1179c1078
Timestamp: 1664329783 Timestamp [UCT]: 2022-09-28 01:49:43 Age [y:d:h:m:s]: 02:173:09:49:14
Block: 597228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645448 RingCT/type: yes/0
Extra: 01a61580986db4f2ae88034d2d9511fbd4b52fa361f224ea4b5b7aefa1179c1078021100000006faf35c9c000000000000000000

1 output(s) for total of 6.443706914000 dcy

stealth address amount amount idx
00: 6e5cb5aa2d67c8d99e9b4f672f45de5c0d2856a2b51f374044ab4221f141b64d 6.443706914000 1032605 of 0

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": 597238, "vin": [ { "gen": { "height": 597228 } } ], "vout": [ { "amount": 6443706914, "target": { "key": "6e5cb5aa2d67c8d99e9b4f672f45de5c0d2856a2b51f374044ab4221f141b64d" } } ], "extra": [ 1, 166, 21, 128, 152, 109, 180, 242, 174, 136, 3, 77, 45, 149, 17, 251, 212, 181, 47, 163, 97, 242, 36, 234, 75, 91, 122, 239, 161, 23, 156, 16, 120, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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