Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44cec83a3103060987770e93eef57d5b70d71d7b4a1ab6d09ffc32fba05d8462

Tx prefix hash: 5b4fb9da8cbbaefb6d12cab635df29ac3ab2e5b50de66dcfe6593b2c547f2d8d
Tx public key: 7b21192cc94a694c0f77ba2ba0cc1d9a4292fafb23741e65f887406da47f2aba
Timestamp: 1583629354 Timestamp [UCT]: 2020-03-08 01:02:34 Age [y:d:h:m:s]: 05:041:01:35:01
Block: 78155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184970 RingCT/type: yes/0
Extra: 017b21192cc94a694c0f77ba2ba0cc1d9a4292fafb23741e65f887406da47f2aba02110000000227105131000000000000000000

1 output(s) for total of 338.096623801000 dcy

stealth address amount amount idx
00: b90d0d505258427d8feb2c9dc4763a724a2cb96a95e2c8311c4e0a8059349b28 338.096623801000 143587 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": 78165, "vin": [ { "gen": { "height": 78155 } } ], "vout": [ { "amount": 338096623801, "target": { "key": "b90d0d505258427d8feb2c9dc4763a724a2cb96a95e2c8311c4e0a8059349b28" } } ], "extra": [ 1, 123, 33, 25, 44, 201, 74, 105, 76, 15, 119, 186, 43, 160, 204, 29, 154, 66, 146, 250, 251, 35, 116, 30, 101, 248, 135, 64, 109, 164, 127, 42, 186, 2, 17, 0, 0, 0, 2, 39, 16, 81, 49, 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