Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388e952cf0754ba3b8b83df512a5208441e9ef7438612f7684a908b928839476

Tx prefix hash: 5754ca775f162097b0c40af270af061fc838fb9fcc3489d099fa6743fa2dca7c
Tx public key: 26e12e681d6fa57c1ff783a50c7e3fc055e7bb55ebf3df9b18c3a826ba2f0d72
Timestamp: 1725360145 Timestamp [UCT]: 2024-09-03 10:42:25 Age [y:d:h:m:s]: 00:209:08:27:22
Block: 1102003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149460 RingCT/type: yes/0
Extra: 0126e12e681d6fa57c1ff783a50c7e3fc055e7bb55ebf3df9b18c3a826ba2f0d72021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf15c158d1e1593854e90357611a4545f97a2071b727d3e140330f0d41664c0 0.600000000000 1578266 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": 1102013, "vin": [ { "gen": { "height": 1102003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf15c158d1e1593854e90357611a4545f97a2071b727d3e140330f0d41664c0" } } ], "extra": [ 1, 38, 225, 46, 104, 29, 111, 165, 124, 31, 247, 131, 165, 12, 126, 63, 192, 85, 231, 187, 85, 235, 243, 223, 155, 24, 195, 168, 38, 186, 47, 13, 114, 2, 17, 0, 0, 0, 4, 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