Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f412ba5598f48c1ffe75dc04bfc89a92b7218c272582edd2132b6971352d041

Tx prefix hash: 356703987a4a2e0219ba2700516a76bfcf5e8753688bcd2d2b887634b894edcf
Tx public key: 6b3905656f64889ce725b7dfe234fd2b79b8a5f0b482335f7c1fd3b8d2473568
Timestamp: 1727943357 Timestamp [UCT]: 2024-10-03 08:15:57 Age [y:d:h:m:s]: 00:162:01:46:45
Block: 1123409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115641 RingCT/type: yes/0
Extra: 016b3905656f64889ce725b7dfe234fd2b79b8a5f0b482335f7c1fd3b8d2473568021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a50e21d76e2e7f6313ba0aa1c67cf97ee31f0ebce3bbfeea3acdc910ca20668 0.600000000000 1605942 of 15

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": 1123419, "vin": [ { "gen": { "height": 1123409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a50e21d76e2e7f6313ba0aa1c67cf97ee31f0ebce3bbfeea3acdc910ca20668" } } ], "extra": [ 1, 107, 57, 5, 101, 111, 100, 136, 156, 231, 37, 183, 223, 226, 52, 253, 43, 121, 184, 165, 240, 180, 130, 51, 95, 124, 31, 211, 184, 210, 71, 53, 104, 2, 17, 0, 0, 0, 3, 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