Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5b334ef329085713fd7b8dd4efe146803e9248f39e989cf8c54952d8c442e7b

Tx prefix hash: 6462871fc2543ccb3d24af9f3395ec2aef4323ac1cfa5a6f8711bfefe3a47f3d
Tx public key: 00281d55ebd0ba9972b595970e948136e3b2330b38e20fb97f743ea965caeed6
Timestamp: 1714536637 Timestamp [UCT]: 2024-05-01 04:10:37 Age [y:d:h:m:s]: 00:245:01:54:06
Block: 1012264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175411 RingCT/type: yes/0
Extra: 0100281d55ebd0ba9972b595970e948136e3b2330b38e20fb97f743ea965caeed602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79c6bbcf6bf5c7b763b01b8e14ee8ad566a6454263267b4bd5db6d0f90fc295b 0.600000000000 1474736 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": 1012274, "vin": [ { "gen": { "height": 1012264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79c6bbcf6bf5c7b763b01b8e14ee8ad566a6454263267b4bd5db6d0f90fc295b" } } ], "extra": [ 1, 0, 40, 29, 85, 235, 208, 186, 153, 114, 181, 149, 151, 14, 148, 129, 54, 227, 178, 51, 11, 56, 226, 15, 185, 127, 116, 62, 169, 101, 202, 238, 214, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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