Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a6521e44451a3bfcaf2f2e57d7c02d2a890ab663ae45c79ce14ee941b068f4

Tx prefix hash: 74dcd57b67c2f3d1c5ac800f2d77d8cd42f031bb4f2d876214ecd6b7e23c997a
Tx public key: bf89698ff0862bbbca5b8ce4c0cea5e62b8e31798b5cd315e8e2c641d76ebf64
Timestamp: 1674709262 Timestamp [UCT]: 2023-01-26 05:01:02 Age [y:d:h:m:s]: 02:310:22:26:04
Block: 682950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 741611 RingCT/type: yes/0
Extra: 01bf89698ff0862bbbca5b8ce4c0cea5e62b8e31798b5cd315e8e2c641d76ebf64021100000002272bcc39000000000000000000

1 output(s) for total of 3.350449545000 dcy

stealth address amount amount idx
00: aa5dd3ae98e6490b8af65d5d2f35d96ce1176b311f2e43b9b3fa09dd70aa04f4 3.350449545000 1125095 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": 682960, "vin": [ { "gen": { "height": 682950 } } ], "vout": [ { "amount": 3350449545, "target": { "key": "aa5dd3ae98e6490b8af65d5d2f35d96ce1176b311f2e43b9b3fa09dd70aa04f4" } } ], "extra": [ 1, 191, 137, 105, 143, 240, 134, 43, 187, 202, 91, 140, 228, 192, 206, 165, 230, 43, 142, 49, 121, 139, 92, 211, 21, 232, 226, 198, 65, 215, 110, 191, 100, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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