Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4187b9949f74806b601970dc6b4fbaf3f55d94854fbd8c938283837ec7fd4e1d

Tx prefix hash: 0488cdbc090b81f0c30503c8d5dcd64870fa4600fe64df68d2e55265a3f57913
Tx public key: df50255455e69f8cf15e6f0367d5d523d8755ff7c970a405c32d9e467ff97102
Timestamp: 1694239318 Timestamp [UCT]: 2023-09-09 06:01:58 Age [y:d:h:m:s]: 01:130:11:04:14
Block: 844166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354574 RingCT/type: yes/0
Extra: 01df50255455e69f8cf15e6f0367d5d523d8755ff7c970a405c32d9e467ff97102021100000001faf35c9c000000000000000000

1 output(s) for total of 0.979326885000 dcy

stealth address amount amount idx
00: abba8942c721765e0bc631f793ec341c99a66de4a5ce2e34ad4087e14fbe8395 0.979326885000 1297458 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": 844176, "vin": [ { "gen": { "height": 844166 } } ], "vout": [ { "amount": 979326885, "target": { "key": "abba8942c721765e0bc631f793ec341c99a66de4a5ce2e34ad4087e14fbe8395" } } ], "extra": [ 1, 223, 80, 37, 84, 85, 230, 159, 140, 241, 94, 111, 3, 103, 213, 213, 35, 216, 117, 95, 247, 201, 112, 164, 5, 195, 45, 158, 70, 127, 249, 113, 2, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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