Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a8c4e13e475fbc9189c3d7265ef59cfc8189f0c455915817c26bba57b08d9b5

Tx prefix hash: 2088ccb1afd40afc070d61ec9bcab21eed1a0f6ae27bea2c1ded18aa14820c33
Tx public key: 5098c0f5553a356bee4f83c465a4545f6af88e4f0c31f72d55ba9a2759415505
Timestamp: 1682166878 Timestamp [UCT]: 2023-04-22 12:34:38 Age [y:d:h:m:s]: 02:033:15:06:56
Block: 744151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546201 RingCT/type: yes/0
Extra: 015098c0f5553a356bee4f83c465a4545f6af88e4f0c31f72d55ba9a2759415505021100000001faf35c9c000000000000000000

1 output(s) for total of 2.100572352000 dcy

stealth address amount amount idx
00: 9ca2a50ae12153b960877f891be3583030306f80f9e0bdb2ebc38e6a469b94dc 2.100572352000 1191410 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": 744161, "vin": [ { "gen": { "height": 744151 } } ], "vout": [ { "amount": 2100572352, "target": { "key": "9ca2a50ae12153b960877f891be3583030306f80f9e0bdb2ebc38e6a469b94dc" } } ], "extra": [ 1, 80, 152, 192, 245, 85, 58, 53, 107, 238, 79, 131, 196, 101, 164, 84, 95, 106, 248, 142, 79, 12, 49, 247, 45, 85, 186, 154, 39, 89, 65, 85, 5, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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