Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba3613eb0314b34cbc23c3d4f96435ba920fe1fd8473490d4f532ee853b2844

Tx prefix hash: a2243b7141e74574eff7ecfd1b2f94c4cd7788cb4f178a2fde977240319745e6
Tx public key: 4b2c645b1dc822336dc7446bcd595ee5234eed50b97e5d177f03d12f330010e5
Timestamp: 1681469030 Timestamp [UCT]: 2023-04-14 10:43:50 Age [y:d:h:m:s]: 01:358:14:56:33
Block: 738353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517582 RingCT/type: yes/0
Extra: 014b2c645b1dc822336dc7446bcd595ee5234eed50b97e5d177f03d12f330010e5021100000002b3164c24000000000000000000

1 output(s) for total of 2.195483746000 dcy

stealth address amount amount idx
00: 3cb6d0664ab32f4e776a19ae3febd0455ab6c4d66b03213d27accb2460eb0cf7 2.195483746000 1185032 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": 738363, "vin": [ { "gen": { "height": 738353 } } ], "vout": [ { "amount": 2195483746, "target": { "key": "3cb6d0664ab32f4e776a19ae3febd0455ab6c4d66b03213d27accb2460eb0cf7" } } ], "extra": [ 1, 75, 44, 100, 91, 29, 200, 34, 51, 109, 199, 68, 107, 205, 89, 94, 229, 35, 78, 237, 80, 185, 126, 93, 23, 127, 3, 209, 47, 51, 0, 16, 229, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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