Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dbe8b1294c5c07e949641576d59c5dd0ec7ca9c64056abd3ee8acd23045f8e9

Tx prefix hash: bf90dfb7513d8fbea097f92d495e0ea8248c2a22127c873dcafe1b1e27f5edbf
Tx public key: 5dcca8919ed26dbabd94cab019d4c88b8e5642ba1088eba132df65efae127fae
Timestamp: 1636638705 Timestamp [UCT]: 2021-11-11 13:51:45 Age [y:d:h:m:s]: 03:124:02:10:29
Block: 372137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 867095 RingCT/type: yes/0
Extra: 015dcca8919ed26dbabd94cab019d4c88b8e5642ba1088eba132df65efae127fae021100000002745f00f8000000000000000000

1 output(s) for total of 35.889379651000 dcy

stealth address amount amount idx
00: f4307d29b4923aaafd2d2621fab89461832d741cedda918e6066d72aeeecb343 35.889379651000 753905 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": 372147, "vin": [ { "gen": { "height": 372137 } } ], "vout": [ { "amount": 35889379651, "target": { "key": "f4307d29b4923aaafd2d2621fab89461832d741cedda918e6066d72aeeecb343" } } ], "extra": [ 1, 93, 204, 168, 145, 158, 210, 109, 186, 189, 148, 202, 176, 25, 212, 200, 139, 142, 86, 66, 186, 16, 136, 235, 161, 50, 223, 101, 239, 174, 18, 127, 174, 2, 17, 0, 0, 0, 2, 116, 95, 0, 248, 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