Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7564bd0ec4834fa0eb25481b2119a38f36ca903ad93f2a39f7f9e56323ac78

Tx prefix hash: 5714be212f96fa03d5e4834b921e0bd1a86ba0def5f849f01ce8f1d22f12aa94
Tx public key: 2527b24e0a1621980e1309b628e6277126f51eaa617ccfd4ff7636f903279ed3
Timestamp: 1685970704 Timestamp [UCT]: 2023-06-05 13:11:44 Age [y:d:h:m:s]: 02:167:11:07:24
Block: 775683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639483 RingCT/type: yes/0
Extra: 012527b24e0a1621980e1309b628e6277126f51eaa617ccfd4ff7636f903279ed302110000000133af99f4000000000000000000

1 output(s) for total of 1.651354770000 dcy

stealth address amount amount idx
00: c08822871752715a1a612539f4dd33c107f6aa93cd4772dc4da520c6da707963 1.651354770000 1225204 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": 775693, "vin": [ { "gen": { "height": 775683 } } ], "vout": [ { "amount": 1651354770, "target": { "key": "c08822871752715a1a612539f4dd33c107f6aa93cd4772dc4da520c6da707963" } } ], "extra": [ 1, 37, 39, 178, 78, 10, 22, 33, 152, 14, 19, 9, 182, 40, 230, 39, 113, 38, 245, 30, 170, 97, 124, 207, 212, 255, 118, 54, 249, 3, 39, 158, 211, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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