Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 743dc6c5b8ac0d81ea8d938687c249dddd0ba9edcffc79c9bf72db1788979213

Tx prefix hash: a4683e44a56995c315cf75771d547f5d70675d4b72470b80d549fb8754c5608f
Tx public key: a65a6d2733200aa9163a0975cda08a4120fd4ed92d8562be12f2d3236ed21b2f
Timestamp: 1707176849 Timestamp [UCT]: 2024-02-05 23:47:29 Age [y:d:h:m:s]: 01:064:12:58:49
Block: 951237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307185 RingCT/type: yes/0
Extra: 01a65a6d2733200aa9163a0975cda08a4120fd4ed92d8562be12f2d3236ed21b2f0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4531b1e4b700f4d4c2fc212d71e4182fb23bc624aaaded09cadecbeb74d81502 0.600000000000 1409975 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": 951247, "vin": [ { "gen": { "height": 951237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4531b1e4b700f4d4c2fc212d71e4182fb23bc624aaaded09cadecbeb74d81502" } } ], "extra": [ 1, 166, 90, 109, 39, 51, 32, 10, 169, 22, 58, 9, 117, 205, 160, 138, 65, 32, 253, 78, 217, 45, 133, 98, 190, 18, 242, 211, 35, 110, 210, 27, 47, 2, 17, 0, 0, 0, 8, 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