Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1891cd55e0a981a42f97a9f5c7eeb673e2d33c46b42b5d670f99241d98aecd2b

Tx prefix hash: 79a86a2f9d44f20eaca3e873877f51d54ce062950bc7066de1cbc795cf5fd8db
Tx public key: c80775093ca094a7212ad2ea58b0d641e258a5b4a36a12ff02c45767c0797718
Timestamp: 1718797957 Timestamp [UCT]: 2024-06-19 11:52:37 Age [y:d:h:m:s]: 00:186:16:44:54
Block: 1047598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133633 RingCT/type: yes/0
Extra: 01c80775093ca094a7212ad2ea58b0d641e258a5b4a36a12ff02c45767c07977180211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434c27867b6e5f116f13b058a2ae1848dcaf6e768cff86772989f150721c30a2 0.600000000000 1517463 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": 1047608, "vin": [ { "gen": { "height": 1047598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434c27867b6e5f116f13b058a2ae1848dcaf6e768cff86772989f150721c30a2" } } ], "extra": [ 1, 200, 7, 117, 9, 60, 160, 148, 167, 33, 42, 210, 234, 88, 176, 214, 65, 226, 88, 165, 180, 163, 106, 18, 255, 2, 196, 87, 103, 192, 121, 119, 24, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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