Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688f7302b055ea7b447b5a7d69779b25d058742761b57f6b7e399f173dcafb5f

Tx prefix hash: b3d42b165b62b39525f468cefd894bcaf7ad3831c494ddb74b21efc064ffa494
Tx public key: 476944209aeffcec9c1d1b968df95e3bdc85269bf8c8683096a4d6612e9839ed
Timestamp: 1682605345 Timestamp [UCT]: 2023-04-27 14:22:25 Age [y:d:h:m:s]: 02:011:20:02:58
Block: 747787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530601 RingCT/type: yes/0
Extra: 01476944209aeffcec9c1d1b968df95e3bdc85269bf8c8683096a4d6612e9839ed021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.043014525000 dcy

stealth address amount amount idx
00: 5869688184843eeedcbbcf3f7ea37cd48610c371e74ac9409b5546267cfc18e3 2.043014525000 1195542 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": 747797, "vin": [ { "gen": { "height": 747787 } } ], "vout": [ { "amount": 2043014525, "target": { "key": "5869688184843eeedcbbcf3f7ea37cd48610c371e74ac9409b5546267cfc18e3" } } ], "extra": [ 1, 71, 105, 68, 32, 154, 239, 252, 236, 156, 29, 27, 150, 141, 249, 94, 59, 220, 133, 38, 155, 248, 200, 104, 48, 150, 164, 214, 97, 46, 152, 57, 237, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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