Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfae1f581c23c0cda8ab38f0aad1f70f3a7a956566536d7c5393dbb53d672bdb

Tx prefix hash: cd9b44870be6d31171488b4dc58b7bf40fe3fa28499ed1f4d6ccdaf80fe3bf3a
Tx public key: 6e778bcf4f151caa691e86b8332bc3baf00ad1718deac3a0143b4e140d9c5303
Timestamp: 1662165037 Timestamp [UCT]: 2022-09-03 00:30:37 Age [y:d:h:m:s]: 02:091:19:39:23
Block: 579564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587084 RingCT/type: yes/0
Extra: 016e778bcf4f151caa691e86b8332bc3baf00ad1718deac3a0143b4e140d9c5303021100000001a0a5d876000000000000000000

1 output(s) for total of 7.373335041000 dcy

stealth address amount amount idx
00: 61c41d639eaa32f2758c35d6fd1a57d74e82da9fd96af1e272109b3f7bab5f2d 7.373335041000 1013034 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": 579574, "vin": [ { "gen": { "height": 579564 } } ], "vout": [ { "amount": 7373335041, "target": { "key": "61c41d639eaa32f2758c35d6fd1a57d74e82da9fd96af1e272109b3f7bab5f2d" } } ], "extra": [ 1, 110, 119, 139, 207, 79, 21, 28, 170, 105, 30, 134, 184, 51, 43, 195, 186, 240, 10, 209, 113, 141, 234, 195, 160, 20, 59, 78, 20, 13, 156, 83, 3, 2, 17, 0, 0, 0, 1, 160, 165, 216, 118, 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