Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fdaea26b5c3ee0e5ef63a56e1e6eadd153db5378d7ac9ca077065c3b534b6a5

Tx prefix hash: 6e154c5bb074863381bb0734381900747abcae3debad29dc40b7beb448826cd9
Tx public key: fef74cdb2bffad023f7b3a6b52c217b05d36bc239875e8e9d36886c321732f55
Timestamp: 1730053840 Timestamp [UCT]: 2024-10-27 18:30:40 Age [y:d:h:m:s]: 00:147:23:56:59
Block: 1140870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105559 RingCT/type: yes/0
Extra: 01fef74cdb2bffad023f7b3a6b52c217b05d36bc239875e8e9d36886c321732f55021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d555c281fa1e29b3545ba872baa9bf40eeef1482346b7eaae0dd82e610657344 0.600000000000 1624673 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": 1140880, "vin": [ { "gen": { "height": 1140870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d555c281fa1e29b3545ba872baa9bf40eeef1482346b7eaae0dd82e610657344" } } ], "extra": [ 1, 254, 247, 76, 219, 43, 255, 173, 2, 63, 123, 58, 107, 82, 194, 23, 176, 93, 54, 188, 35, 152, 117, 232, 233, 211, 104, 134, 195, 33, 115, 47, 85, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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