Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf92c6f3091a3a573456246f87b1231bdc7acd3cab10d9cffb7da6393c5fedd

Tx prefix hash: 686b8a6649b8f7ec891638c30d943e8145f9cf4ef2430ff5f54b0f963e125cc8
Tx public key: f782273ab7391699eeaec815b5ef44d4027b1d74c59552c303b5629191fd3dde
Timestamp: 1696630173 Timestamp [UCT]: 2023-10-06 22:09:33 Age [y:d:h:m:s]: 01:169:01:49:37
Block: 864009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381864 RingCT/type: yes/0
Extra: 01f782273ab7391699eeaec815b5ef44d4027b1d74c59552c303b5629191fd3dde0211000000014b8f5122000000000000000000

1 output(s) for total of 0.841743075000 dcy

stealth address amount amount idx
00: a333fea171007728aeb2462c7217392f0c6532003359a5105d1dd7060989d6ee 0.841743075000 1318513 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": 864019, "vin": [ { "gen": { "height": 864009 } } ], "vout": [ { "amount": 841743075, "target": { "key": "a333fea171007728aeb2462c7217392f0c6532003359a5105d1dd7060989d6ee" } } ], "extra": [ 1, 247, 130, 39, 58, 183, 57, 22, 153, 238, 174, 200, 21, 181, 239, 68, 212, 2, 123, 29, 116, 197, 149, 82, 195, 3, 181, 98, 145, 145, 253, 61, 222, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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