Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc511b713b3a1c3ebae2d0b139c3849f1c89eeda09d1437bbef0e6be41bd8a7

Tx prefix hash: 005b1d8ac269c7e11231b566e3c506f1e6af38a58cae190c268b23a4bcd9be96
Tx public key: 2ccd337982a73033412c1ed37a32ec56a80b43f0529a7056b4763f0ed9008cea
Timestamp: 1680979281 Timestamp [UCT]: 2023-04-08 18:41:21 Age [y:d:h:m:s]: 01:226:17:45:49
Block: 734351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423463 RingCT/type: yes/0
Extra: 012ccd337982a73033412c1ed37a32ec56a80b43f0529a7056b4763f0ed9008cea02110000000bb3164c24000000000000000000

1 output(s) for total of 2.263552227000 dcy

stealth address amount amount idx
00: 2b029a12d34135f2ad2dd1555b92eb91c194ccd2aaa7bd12fc611cc44b1113c4 2.263552227000 1180542 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": 734361, "vin": [ { "gen": { "height": 734351 } } ], "vout": [ { "amount": 2263552227, "target": { "key": "2b029a12d34135f2ad2dd1555b92eb91c194ccd2aaa7bd12fc611cc44b1113c4" } } ], "extra": [ 1, 44, 205, 51, 121, 130, 167, 48, 51, 65, 44, 30, 211, 122, 50, 236, 86, 168, 11, 67, 240, 82, 154, 112, 86, 180, 118, 63, 14, 217, 0, 140, 234, 2, 17, 0, 0, 0, 11, 179, 22, 76, 36, 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