Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 538d0c9506010b02946985bfd7d22cd4fed799601e610f2cf0ce2e708ce14e1f

Tx prefix hash: 376ee26de18c79308e80a3fcfd6551d5d80420fd8217c26d9500562ff2126520
Tx public key: af5efd902c25c962083f692a97acb270d1ddd7d905d994867ea3f0c3ef4b97c0
Timestamp: 1725441132 Timestamp [UCT]: 2024-09-04 09:12:12 Age [y:d:h:m:s]: 00:214:23:56:57
Block: 1102673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153489 RingCT/type: yes/0
Extra: 01af5efd902c25c962083f692a97acb270d1ddd7d905d994867ea3f0c3ef4b97c002110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a99209eaf1e2862e599c15962e2df0ff3dbdac7253067380a1bec6febd063f9 0.600000000000 1579200 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": 1102683, "vin": [ { "gen": { "height": 1102673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a99209eaf1e2862e599c15962e2df0ff3dbdac7253067380a1bec6febd063f9" } } ], "extra": [ 1, 175, 94, 253, 144, 44, 37, 201, 98, 8, 63, 105, 42, 151, 172, 178, 112, 209, 221, 215, 217, 5, 217, 148, 134, 126, 163, 240, 195, 239, 75, 151, 192, 2, 17, 0, 0, 0, 20, 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