Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e975716be4ebd8ae6bf7e2df8f963b1a26463e2ecb9439c765f493c1f947c7e8

Tx prefix hash: db4a505a1c720110435e82843db9ab744862ac36b1c3fa7f0cebf49587c4639b
Tx public key: aa651a8e086cbc11b3932d025b40213e551508026d4a1c67edddd49285a82ca5
Timestamp: 1728911148 Timestamp [UCT]: 2024-10-14 13:05:48 Age [y:d:h:m:s]: 00:251:11:34:35
Block: 1131439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179355 RingCT/type: yes/0
Extra: 01aa651a8e086cbc11b3932d025b40213e551508026d4a1c67edddd49285a82ca5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 65ced9006ac772393f1917f3e7e9b892d3113fd5990ab30dedebf4972bd7ebb8 0.600010000000 1614338 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": 1131449, "vin": [ { "gen": { "height": 1131439 } } ], "vout": [ { "amount": 600010000, "target": { "key": "65ced9006ac772393f1917f3e7e9b892d3113fd5990ab30dedebf4972bd7ebb8" } } ], "extra": [ 1, 170, 101, 26, 142, 8, 108, 188, 17, 179, 147, 45, 2, 91, 64, 33, 62, 85, 21, 8, 2, 109, 74, 28, 103, 237, 221, 212, 146, 133, 168, 44, 165, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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