Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e44eb537d88a4aecfc279b16fc32a78a642e2b3a7e25a213b991e75595e504

Tx prefix hash: ea66fd3686295ad29ce3ad7c1d51c5acc2440290a74922af10e6f1e651464756
Tx public key: 14db519e78721bb249c2a2a6a7770c287a77e0a9885ae4f800dcc3899fb73959
Timestamp: 1716504350 Timestamp [UCT]: 2024-05-23 22:45:50 Age [y:d:h:m:s]: 00:318:21:19:25
Block: 1028578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227904 RingCT/type: yes/0
Extra: 0114db519e78721bb249c2a2a6a7770c287a77e0a9885ae4f800dcc3899fb739590211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b72c266a077a24b40083770d79357c54b96792daa3fbb2d6848bcc3df0989705 0.600000000000 1496571 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": 1028588, "vin": [ { "gen": { "height": 1028578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b72c266a077a24b40083770d79357c54b96792daa3fbb2d6848bcc3df0989705" } } ], "extra": [ 1, 20, 219, 81, 158, 120, 114, 27, 178, 73, 194, 162, 166, 167, 119, 12, 40, 122, 119, 224, 169, 136, 90, 228, 248, 0, 220, 195, 137, 159, 183, 57, 89, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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