Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b2b660c6100e772aac1c01649b67d4688ba7ad27ceb2dcc1a4db1aa77686aec

Tx prefix hash: fa8506e09ab9848bceb12f4a9f4f4274f3f14a3597670ba6662eb275dff46933
Tx public key: fa76b25f2b1e2fc64b814fb13404041deed80429c885cd70856bce4bdadf802b
Timestamp: 1722157349 Timestamp [UCT]: 2024-07-28 09:02:29 Age [y:d:h:m:s]: 00:246:10:44:41
Block: 1075442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176038 RingCT/type: yes/0
Extra: 01fa76b25f2b1e2fc64b814fb13404041deed80429c885cd70856bce4bdadf802b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10698e5b2e6f09cd22c0a1c4ab8a8a80733547f28be6608f9b75ce7d71e1b72 0.600000000000 1547967 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": 1075452, "vin": [ { "gen": { "height": 1075442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10698e5b2e6f09cd22c0a1c4ab8a8a80733547f28be6608f9b75ce7d71e1b72" } } ], "extra": [ 1, 250, 118, 178, 95, 43, 30, 47, 198, 75, 129, 79, 177, 52, 4, 4, 29, 238, 216, 4, 41, 200, 133, 205, 112, 133, 107, 206, 75, 218, 223, 128, 43, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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