Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d4a51c2ef15d866ecbeb2364bbfbff2ab4aa2066785a210436877ce64d27632

Tx prefix hash: d676fb21cab3b99795e6f32b7339ede7f409259db68094840faae0079af8bc4f
Tx public key: 016a6911d0f6d0e48108d67d408569dfb57d67ccd1f71d0562f543800dbbbd36
Timestamp: 1672653390 Timestamp [UCT]: 2023-01-02 09:56:30 Age [y:d:h:m:s]: 02:099:02:49:48
Block: 665891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592531 RingCT/type: yes/0
Extra: 01016a6911d0f6d0e48108d67d408569dfb57d67ccd1f71d0562f543800dbbbd360211000000028b7b6602000000000000000000

1 output(s) for total of 3.816160709000 dcy

stealth address amount amount idx
00: d6ffea0ec7cf22d0d01c28b06bc3fc8bea6f2f18a018d53e4f92a0ce2a380094 3.816160709000 1106960 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": 665901, "vin": [ { "gen": { "height": 665891 } } ], "vout": [ { "amount": 3816160709, "target": { "key": "d6ffea0ec7cf22d0d01c28b06bc3fc8bea6f2f18a018d53e4f92a0ce2a380094" } } ], "extra": [ 1, 1, 106, 105, 17, 208, 246, 208, 228, 129, 8, 214, 125, 64, 133, 105, 223, 181, 125, 103, 204, 209, 247, 29, 5, 98, 245, 67, 128, 13, 187, 189, 54, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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